- Shows 'Remove Server' button when more than 1 server exists
- Styled with red border/hover to indicate removal action
- Shows -$20/mo badge to indicate cost savings
- Removes the most recently added server

- When auto-scaling is enabled, system now scales up to meet
  minInstances requirement, not just when CPU threshold is exceeded
- This ensures if minInstances is set to 5 with only 2 active servers,
  the system will automatically add servers to reach the minimum

- Added separate useEffect to monitor minInstances changes
- Servers are added automatically (one at a time) when:
  - Auto-scaling is enabled
  - Load balancer is active
  - Current server count < minInstances
- Works even when simulation is paused

- Auto-scaling now scales down when server count exceeds new minInstances
- Removes servers one at a time with 500ms delay
- Still maintains at least 1 server

The second useEffect was unconditionally scaling down servers when
count exceeded minInstances, which conflicted with the CPU-based
auto-scaling in the game loop. Now the useEffect only handles
scaling UP to meet minimum requirements, while CPU-based scale-up
and scale-down remain controlled by the game loop thresholds.

- Calculate avgLoad synchronously before state update (was using stale data)
- Reduce scaleUpDelay from 30s to 5s for faster response to spikes
- The CPU threshold check now uses current tick's load, not previous tick

Displays all component prices (CPU, RAM, disk, network) in a clear
grid layout so users understand costs before upgrading.